View Issue Details

IDProjectCategoryView StatusLast Update
0001947T99X171.00 SKB EagleSW Issuepublic2024-05-16 11:04
Reporter(ALTech) JunGyu Kim Assigned To(SW) Peter ChenDue Date2024-05-20 15:37
PrioritynormalSeveritys4-minorReproducibilityrandom
Status closedResolutionfixed 
Summary0001947: [Smart3][ATV12] BT RCU disconnected after power reboot at passive standby
DescriptionHi Peter,

After apply below ticket, after cold booting at passive standby mode, BT connection is not possible sometimes.
https://btracker-cns.fii-foxconn.com/vaas/view.php?id=1909

1) Passive standby mode > After cold boot, wait for BT connection and try NUGU 25 times after 30 seconds:
    > RCU and BT are disconnected, pairing is possible when attempting pairing again => occurrs 7 times
    > RCU does not work at all and pairing does not work => occurrs 1 time

2) Passive standby mode > After cold boot, try NUGU 10 times before connecting to BT:
    > RCU and BT are disconnected, pairing is possible when attempting pairing again => occurrs 10 times

Please check this issue.

Thank you.
Kim
TagsNo tags attached.
Attach Tags

Users monitoring this issue

Activities

(ALTech) JunGyu Kim

2024-05-13 14:44

developer   ~0015765

Hi Peter,

Our QA tested today again in same FW and reproduce rate reduced.
Today : RCU and BT are disconnected, pairing is possible when attempting pairing again => Occurs 1 time in 20 times

Thank you.
Kim

(SW) Peter Chen

2024-05-14 15:44

developer   ~0015793

Last edited: 2024-05-14 15:48

Hi JunGyu,

Please help to share the log and check if this issue can be reproduced without the patch from https://btracker-cns.fii-foxconn.com/vaas/view.php?id=1909.

The correct process for that NUGU can work should be device boot completed -> BT connected -> NUGU audio device registered

This is "BT connection" issue and the Mantis ticket(https://btracker-cns.fii-foxconn.com/vaas/view.php?id=1909) is "NUGU audio device registered" issue.

Thanks,

(ALTech) JunGyu Kim

2024-05-16 11:04

developer   ~0015800

Hi Peter,

Our QA test again in FW 15.542.52 and this issue is not reproduced.
I think it seems related with RF condition.

So I will close this issue.
Thank you for support.
Kim

Issue History

Date Modified Username Field Change
2024-05-13 14:41 (ALTech) JunGyu Kim New Issue
2024-05-13 14:41 (ALTech) JunGyu Kim Status new => assigned
2024-05-13 14:41 (ALTech) JunGyu Kim Assigned To => (SW) Peter Chen
2024-05-13 14:43 (ALTech) JunGyu Kim Issue Monitored: (ALTech) SY Yoon
2024-05-13 14:43 (ALTech) JunGyu Kim Issue Monitored: (ALTech) Younkwang Jung
2024-05-13 14:43 (ALTech) JunGyu Kim Issue Monitored: (ALTech) Sangmin Choi
2024-05-13 14:44 (ALTech) JunGyu Kim Issue Monitored: (ALTech) Wooshin Kang
2024-05-13 14:44 (ALTech) JunGyu Kim Note Added: 0015765
2024-05-14 15:44 (SW) Peter Chen Note Added: 0015793
2024-05-14 15:48 (SW) Peter Chen Note Edited: 0015793
2024-05-16 11:04 (ALTech) JunGyu Kim Status assigned => closed
2024-05-16 11:04 (ALTech) JunGyu Kim Resolution open => fixed
2024-05-16 11:04 (ALTech) JunGyu Kim Note Added: 0015800